home *** CD-ROM | disk | FTP | other *** search
- Path: charnel.ecst.csuchico.edu!csusac!walkers
- From: walkers@ecs.ecs.csus.edu (Sean Walker)
- Newsgroups: comp.sys.amiga.audio
- Subject: Re: IP aliasing
- Date: 21 Feb 1996 18:23:34 GMT
- Organization: California State University, Sacramento
- Message-ID: <4gfnv6$ial@csusac.ecs.csus.edu>
- References: <4farkg$2pc@csusac.ecs.csus.edu> <4g1lsd$bt4@serpens.rhein.de> <4g7lnp$p4q@news.jhu.edu> <4g7qtd$d0@serpens.rhein.de> <4g99va$2b9@news.jhu.edu> <4gc6i2$fm1@serpens.rhein.de>
- NNTP-Posting-Host: gaia.ecs.csus.edu
- X-Newsreader: TIN [version 1.2 PL2]
-
- Michael van Elst (mlelstv@serpens.rhein.de) wrote:
- > robodude@deanwong.rad.jhu.edu (Zsolt Szabo) writes:
-
- > >>>Nevertheless, it's netmasking that's used in conjunction with SLIP/PPP,
- > >>>not ip aliasing.
- > >>
- > >>Both is used and the original poster explicitely requested ip aliasing.
-
- > >Still, the most sensible solution to his particular problem is a subnet,
- > >i.e. netmasking.
-
- > No. A subnet is no solution because a subnet has to be routed. The original
- > poster explicitely requested ip aliasing _so that the provider does not
- > have to route another ip address_.
-
- > --
- > Michael van Elst
-
- > Internet: mlelstv@serpens.rhein.de
- > "A potential Snark may lurk in every tree."
-
- Sorry about my original post ending up in the wrong group, I guess I
- clicked on the wrong name. A subnet, of course, requires all sorts of
- special stuff, router, etc. while IP Aliasing is a technique very much
- like firewalling. I have done some nice (read: boring) reading about
- firewalling and all that stuff. I am on a Novell network at work and
- have a crappy ARP server that does not allow multiple IP's/NIC. That
- right there causes many problems. This is not pertinant to my project,
- but is my experiment ground. I guess the only way to set this up to my
- knowledge is to set up a firewall and a proxy server. This will allow
- all users on the inside of the firewall to have their own virtual IP
- address, but each request is routed through the firewall. Telnet's, by
- this method, are indirect. You must telnet to the firewall machine and
- then telnet to another external machine. Web browsers can utilize a
- proxy, and I guess this could work. What a fun project, huh?
-
-
- --
- ______________ ____________________________________
- ( \ / | |
- _)EAN \/\/ALKER| walkers@gaia.ecs.csus.edu |
- | Amiga1200 | http://gaia.ecs.csus.edu/~walkers/ |
- |______________|____________________________________|
-